Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efe62564dcfa6fedb995ef1e482618f5a9c1fa909fd90d325e23ed3155e004f5

Tx prefix hash: 06b038eeb332e50e447a4a9b989ca03e62308cff916951c52a6f47b0a3f43faf
Tx public key: 73a8061fc058812d9c6aeffa9450ece067b5f0f2939a94c09521f80608d7c396
Timestamp: 1749809462 Timestamp [UCT]: 2025-06-13 10:11:02 Age [y:d:h:m:s]: 00:161:06:45:13
Block: 1304081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112998 RingCT/type: yes/0
Extra: 0173a8061fc058812d9c6aeffa9450ece067b5f0f2939a94c09521f80608d7c396021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2c57e867ba65cde5fa7348ce879b5fcb5fe47f62a968f0e4045d16739373d82 0.600000000000 1791666 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": 1304091, "vin": [ { "gen": { "height": 1304081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2c57e867ba65cde5fa7348ce879b5fcb5fe47f62a968f0e4045d16739373d82" } } ], "extra": [ 1, 115, 168, 6, 31, 192, 88, 129, 45, 156, 106, 239, 250, 148, 80, 236, 224, 103, 181, 240, 242, 147, 154, 148, 192, 149, 33, 248, 6, 8, 215, 195, 150, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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