Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37c2c72aa6386d9ca756884c53bdd8f304f9021d759b0a63893417e5ef169c23

Tx prefix hash: 8093aad65cbc90a5f82930956a29f70ca81ed48b9d8723f8043897fbe5b92268
Tx public key: 034be589fcddbffdd5f76dfd953a37db06b9fa9021dcfb5e699678c21bcc8eb7
Timestamp: 1730789287 Timestamp [UCT]: 2024-11-05 06:48:07 Age [y:d:h:m:s]: 00:141:11:19:28
Block: 1146909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100932 RingCT/type: yes/0
Extra: 01034be589fcddbffdd5f76dfd953a37db06b9fa9021dcfb5e699678c21bcc8eb7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 543b43ad2e14d5dd5fc5ca83d20e4d0805b3af09780b3bb305acc985d5dcc6a6 0.600000000000 1631602 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": 1146919, "vin": [ { "gen": { "height": 1146909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "543b43ad2e14d5dd5fc5ca83d20e4d0805b3af09780b3bb305acc985d5dcc6a6" } } ], "extra": [ 1, 3, 75, 229, 137, 252, 221, 191, 253, 213, 247, 109, 253, 149, 58, 55, 219, 6, 185, 250, 144, 33, 220, 251, 94, 105, 150, 120, 194, 27, 204, 142, 183, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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