Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d28398405f5fb16210e36a70648e1d1c0e3440ea9b1637ac1af44077ac34e47

Tx prefix hash: cf0a86daa968462248835d48a9809de9cbea5c18de6761ccfa6ed6b5784e75ec
Tx public key: f8c552f408f7ed8d6fca57fd70108f30439b3f080b7b2bec8c13c6c04446ddd3
Timestamp: 1717104364 Timestamp [UCT]: 2024-05-30 21:26:04 Age [y:d:h:m:s]: 00:298:22:39:22
Block: 1033547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213642 RingCT/type: yes/0
Extra: 01f8c552f408f7ed8d6fca57fd70108f30439b3f080b7b2bec8c13c6c04446ddd302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1afc069955130ebf5851d73e1d7ecfc67682da3ae538544cb549ea2b0bffb3fa 0.600000000000 1502016 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": 1033557, "vin": [ { "gen": { "height": 1033547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1afc069955130ebf5851d73e1d7ecfc67682da3ae538544cb549ea2b0bffb3fa" } } ], "extra": [ 1, 248, 197, 82, 244, 8, 247, 237, 141, 111, 202, 87, 253, 112, 16, 143, 48, 67, 155, 63, 8, 11, 123, 43, 236, 140, 19, 198, 192, 68, 70, 221, 211, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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