Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b4c5d572a3c55547b23ad9480e67940acd7a697482307024375990120062ae84

Tx prefix hash: 0654281f2e3b53c1258c32d82bfa1a92c5e4bad48a1e5f4dffbda8116217113c
Tx public key: de85ebac71a13c008eb32d143b4d8128b978b365cf15643000d0e9a5eef2a6e8
Timestamp: 1742415810 Timestamp [UCT]: 2025-03-19 20:23:30 Age [y:d:h:m:s]: 00:235:04:00:03
Block: 1242945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165775 RingCT/type: yes/0
Extra: 01de85ebac71a13c008eb32d143b4d8128b978b365cf15643000d0e9a5eef2a6e802110000000ded95dce7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4a3cfef34ac1d2ef07b964128c073a8fa5fb8d6dbe2d91de63b0056f6fbd748 0.600000000000 1729924 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1242955, "vin": [ { "gen": { "height": 1242945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4a3cfef34ac1d2ef07b964128c073a8fa5fb8d6dbe2d91de63b0056f6fbd748" } } ], "extra": [ 1, 222, 133, 235, 172, 113, 161, 60, 0, 142, 179, 45, 20, 59, 77, 129, 40, 185, 120, 179, 101, 207, 21, 100, 48, 0, 208, 233, 165, 238, 242, 166, 232, 2, 17, 0, 0, 0, 13, 237, 149, 220, 231, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8