Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d91d5cc00a920ff8f1640cc2f5e04433504226d7cc7127dce11102e7c61407b1

Tx prefix hash: c7fe8aa940613969b0a8bd4627685350b919d9f54c81921bb41d76174d8a1b94
Tx public key: f3322ea5a7be0460cf7c98d8988daacc72c02785f82601c4ca9e402268a4982c
Timestamp: 1729713839 Timestamp [UCT]: 2024-10-23 20:03:59 Age [y:d:h:m:s]: 00:031:19:56:51
Block: 1138058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22738 RingCT/type: yes/0
Extra: 01f3322ea5a7be0460cf7c98d8988daacc72c02785f82601c4ca9e402268a4982c02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cfe8e0b5596fa0cd5e46fa6e18b9ecde5ec74a5591c68b80dce0206e399a47e 0.600000000000 1621663 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": 1138068, "vin": [ { "gen": { "height": 1138058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cfe8e0b5596fa0cd5e46fa6e18b9ecde5ec74a5591c68b80dce0206e399a47e" } } ], "extra": [ 1, 243, 50, 46, 165, 167, 190, 4, 96, 207, 124, 152, 216, 152, 141, 170, 204, 114, 192, 39, 133, 248, 38, 1, 196, 202, 158, 64, 34, 104, 164, 152, 44, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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