Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e04f18117b41b296d3dbe856778c185610ab8e5d9e740a7b912f91297fc1159

Tx prefix hash: a6c3a2ebea0442da8a512c902e1ad1873e29b72f9ca051489a7ac43c54ce1dd4
Tx public key: e9c5767aff2eb7ecff9bf05d286c45d91d3f26c344feefd97fcc76dde50d6f63
Timestamp: 1749488806 Timestamp [UCT]: 2025-06-09 17:06:46 Age [y:d:h:m:s]: 00:157:23:48:16
Block: 1301481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110594 RingCT/type: yes/0
Extra: 01e9c5767aff2eb7ecff9bf05d286c45d91d3f26c344feefd97fcc76dde50d6f6302110000000cbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb7d22635900efefef7668afea5fcbd7ce3144d4df534426a45a76f820e8fda 0.600000000000 1789040 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": 1301491, "vin": [ { "gen": { "height": 1301481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb7d22635900efefef7668afea5fcbd7ce3144d4df534426a45a76f820e8fda" } } ], "extra": [ 1, 233, 197, 118, 122, 255, 46, 183, 236, 255, 155, 240, 93, 40, 108, 69, 217, 29, 63, 38, 195, 68, 254, 239, 217, 127, 204, 118, 221, 229, 13, 111, 99, 2, 17, 0, 0, 0, 12, 191, 81, 178, 162, 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