Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 755a9386328582ce9e9c5fd7d643c1c35cb80d5b53a78d9c301ace73ffd28f00

Tx prefix hash: 4115501937d0eefc1992e9ef9cadc189363e1092f189a7375d1f3635518ff5ba
Tx public key: 73e2cf2e4d48398b567fd5e213d3f129ea24ee09dc9729b359dc6d5f260a234c
Timestamp: 1759625138 Timestamp [UCT]: 2025-10-05 00:45:38 Age [y:d:h:m:s]: 00:003:19:12:51
Block: 1382950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2716 RingCT/type: yes/0
Extra: 0173e2cf2e4d48398b567fd5e213d3f129ea24ee09dc9729b359dc6d5f260a234c02110000000397baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c947a91eaac17300462c64cd6c754e2ded915e2fbbb5f673742a637a0f0ccad 0.600000000000 1871095 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": 1382960, "vin": [ { "gen": { "height": 1382950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c947a91eaac17300462c64cd6c754e2ded915e2fbbb5f673742a637a0f0ccad" } } ], "extra": [ 1, 115, 226, 207, 46, 77, 72, 57, 139, 86, 127, 213, 226, 19, 211, 241, 41, 234, 36, 238, 9, 220, 151, 41, 179, 89, 220, 109, 95, 38, 10, 35, 76, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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