Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f1d87748a0b186db47d61180ac964cd94c6f4d1e9cba7e8c6c28c8f2bf5972d

Tx prefix hash: 21c2a87dc1eeaffb14d5c8111ccf68e04774ba9b4ccfa5bf6c2cbc588d7e5ce3
Tx public key: e55b91bf71eeede0f92d77374b8939f0b36ff5f83b9f3f5b7bb0d41f32b052e9
Timestamp: 1715037371 Timestamp [UCT]: 2024-05-06 23:16:11 Age [y:d:h:m:s]: 01:188:14:33:08
Block: 1016416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393418 RingCT/type: yes/0
Extra: 01e55b91bf71eeede0f92d77374b8939f0b36ff5f83b9f3f5b7bb0d41f32b052e902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 728bf020bc54cc6ee64f1ddbcc34cc281f07e026b5746881376693ba03ef2de1 0.600000000000 1479993 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": 1016426, "vin": [ { "gen": { "height": 1016416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "728bf020bc54cc6ee64f1ddbcc34cc281f07e026b5746881376693ba03ef2de1" } } ], "extra": [ 1, 229, 91, 145, 191, 113, 238, 237, 224, 249, 45, 119, 55, 75, 137, 57, 240, 179, 111, 245, 248, 59, 159, 63, 91, 123, 176, 212, 31, 50, 176, 82, 233, 2, 17, 0, 0, 0, 2, 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