Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fa480c0ad92e414933f354c3b2e31459763128ad40232d545a65ea1f0f6e826

Tx prefix hash: d7f556d1fe05d3c67a5efd78067bc73b9c55cb4054afd575acabcda540b7f391
Tx public key: 5fe2e9e661415d63be4006318e91a795c6a8c097aad77d98249dfa5cf2224456
Timestamp: 1759453495 Timestamp [UCT]: 2025-10-03 01:04:55 Age [y:d:h:m:s]: 00:041:22:53:20
Block: 1381521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30057 RingCT/type: yes/0
Extra: 015fe2e9e661415d63be4006318e91a795c6a8c097aad77d98249dfa5cf2224456021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b34fafe7ba52673b60b3870de4f6a7f2a85d05e1f816ef77d4f6bf866c3fd62 0.600000000000 1869640 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": 1381531, "vin": [ { "gen": { "height": 1381521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b34fafe7ba52673b60b3870de4f6a7f2a85d05e1f816ef77d4f6bf866c3fd62" } } ], "extra": [ 1, 95, 226, 233, 230, 97, 65, 93, 99, 190, 64, 6, 49, 142, 145, 167, 149, 198, 168, 192, 151, 170, 215, 125, 152, 36, 157, 250, 92, 242, 34, 68, 86, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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