Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab49a15b818f68b4e994f1d067daa5658b0df94603f7df9b5b64b262d18e0926

Tx prefix hash: 254a306886ba0e01474e5ba3197f61a8196658bb1ec95d134a11d412138bfd34
Tx public key: 61493f895523a3ffb50a50814f2c2e3666663606d57e53bfb1273814adccbb2a
Timestamp: 1718617056 Timestamp [UCT]: 2024-06-17 09:37:36 Age [y:d:h:m:s]: 00:276:11:56:08
Block: 1046089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197597 RingCT/type: yes/0
Extra: 0161493f895523a3ffb50a50814f2c2e3666663606d57e53bfb1273814adccbb2a0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64cec26f3b34f6db3f142d3826faf5f9b4cb134b6e840b76c8b1832cd259b8a0 0.600000000000 1515848 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": 1046099, "vin": [ { "gen": { "height": 1046089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64cec26f3b34f6db3f142d3826faf5f9b4cb134b6e840b76c8b1832cd259b8a0" } } ], "extra": [ 1, 97, 73, 63, 137, 85, 35, 163, 255, 181, 10, 80, 129, 79, 44, 46, 54, 102, 102, 54, 6, 213, 126, 83, 191, 177, 39, 56, 20, 173, 204, 187, 42, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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