Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d3bf4489b1cc4af258e0c1d399c73fbb196bd373bc7e8c501cff0d5662b0c8f

Tx prefix hash: 59488fefa641d5ad9b96fdf7bbf141dac0bb6c87ad3670c5f6aa489e05ed57b3
Tx public key: 5d13bceee00fab8dc83b5a9db9eda3094f5dbb8eaca080b501324fb268024dd9
Timestamp: 1712478344 Timestamp [UCT]: 2024-04-07 08:25:44 Age [y:d:h:m:s]: 01:051:16:56:55
Block: 995174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297974 RingCT/type: yes/0
Extra: 015d13bceee00fab8dc83b5a9db9eda3094f5dbb8eaca080b501324fb268024dd90211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 374d8a3467381a719991fe76fd8fa082dfb2a6d4207df7e40ac73c466249f3b8 0.600000000000 1455580 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": 995184, "vin": [ { "gen": { "height": 995174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "374d8a3467381a719991fe76fd8fa082dfb2a6d4207df7e40ac73c466249f3b8" } } ], "extra": [ 1, 93, 19, 188, 238, 224, 15, 171, 141, 200, 59, 90, 157, 185, 237, 163, 9, 79, 93, 187, 142, 172, 160, 128, 181, 1, 50, 79, 178, 104, 2, 77, 217, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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