Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b36143dc67a5bd7e02f75b961a748732d45fc9d64063cb8e8b3404853a8901

Tx prefix hash: add7136608ad8134db463c1d3956a96cd2093345a2ea2492d764462ea9e2c03b
Tx public key: d61d2d545f7f4b6079baaad5e83bf934babd5f4217f025bf381693f03fd9b74e
Timestamp: 1707593945 Timestamp [UCT]: 2024-02-10 19:39:05 Age [y:d:h:m:s]: 01:073:01:34:52
Block: 954695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313278 RingCT/type: yes/0
Extra: 01d61d2d545f7f4b6079baaad5e83bf934babd5f4217f025bf381693f03fd9b74e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1adb763e6acc9f0b1e5a1569190225247aabd9983ee20022163a79a18bbd0d16 0.600000000000 1413977 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": 954705, "vin": [ { "gen": { "height": 954695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1adb763e6acc9f0b1e5a1569190225247aabd9983ee20022163a79a18bbd0d16" } } ], "extra": [ 1, 214, 29, 45, 84, 95, 127, 75, 96, 121, 186, 170, 213, 232, 59, 249, 52, 186, 189, 95, 66, 23, 240, 37, 191, 56, 22, 147, 240, 63, 217, 183, 78, 2, 17, 0, 0, 0, 1, 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