Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e59eb95f701a46c74ad673d701b700a5359cb24385a7c532bf1e6f32dfe9e14

Tx prefix hash: 4d66de9c45b363763158c09979dd905872445ebab4635154a7672d0dddc59391
Tx public key: 9ee8fdcf525e75f7e8a9b7b455fe3509900b7d608cc53ddc441f71cf5ba4bc6b
Timestamp: 1716472273 Timestamp [UCT]: 2024-05-23 13:51:13 Age [y:d:h:m:s]: 01:176:17:05:13
Block: 1028324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384886 RingCT/type: yes/0
Extra: 019ee8fdcf525e75f7e8a9b7b455fe3509900b7d608cc53ddc441f71cf5ba4bc6b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ef5aad648da0b2d0ffc3dcb0d866890743478e98d640090a8fa255e9f35a9a2 0.600000000000 1496313 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": 1028334, "vin": [ { "gen": { "height": 1028324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ef5aad648da0b2d0ffc3dcb0d866890743478e98d640090a8fa255e9f35a9a2" } } ], "extra": [ 1, 158, 232, 253, 207, 82, 94, 117, 247, 232, 169, 183, 180, 85, 254, 53, 9, 144, 11, 125, 96, 140, 197, 61, 220, 68, 31, 113, 207, 91, 164, 188, 107, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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