Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1e80a0bf9936a0bb5bad54a1336393ba0175678bad56c77b770ca5f0c18cc4

Tx prefix hash: 45292035e22c0f83cf255818f4439b422b9ccb5dd6edc7f6782a1342ee6afa75
Tx public key: 1ef6f8376ad6d50b9c52847ef9a3bd1ca1f29280bdda4be2df390ae4af9cdb60
Timestamp: 1755978826 Timestamp [UCT]: 2025-08-23 19:53:46 Age [y:d:h:m:s]: 00:089:19:41:55
Block: 1352916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64117 RingCT/type: yes/0
Extra: 011ef6f8376ad6d50b9c52847ef9a3bd1ca1f29280bdda4be2df390ae4af9cdb600211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef0b775f79492d2efd6b37610d96f5c27c1816c2f22cc2e6e4b2eb3bace1a568 0.600000000000 1840885 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": 1352926, "vin": [ { "gen": { "height": 1352916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef0b775f79492d2efd6b37610d96f5c27c1816c2f22cc2e6e4b2eb3bace1a568" } } ], "extra": [ 1, 30, 246, 248, 55, 106, 214, 213, 11, 156, 82, 132, 126, 249, 163, 189, 28, 161, 242, 146, 128, 189, 218, 75, 226, 223, 57, 10, 228, 175, 156, 219, 96, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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