Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17fbd956298af3b95f2e648834060106de5426a77c7fd19264caee73ef5b09ca

Tx prefix hash: 90b3f69fd5eb5df4d9c2c9104fa270a62a94f9e3638cdceafc91abdbb5ad5e23
Tx public key: fb0564bc881863f30cfe15ca1d26204d96cacaf3fc96e00ddd95b1d523f1c3ea
Timestamp: 1712523858 Timestamp [UCT]: 2024-04-07 21:04:18 Age [y:d:h:m:s]: 01:074:01:31:03
Block: 995540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313799 RingCT/type: yes/0
Extra: 01fb0564bc881863f30cfe15ca1d26204d96cacaf3fc96e00ddd95b1d523f1c3ea02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44f010082834e2bb1c0d9e24bffa552ff705ed813aa8e0a31edaae4f9ffe9ebb 0.600000000000 1455950 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": 995550, "vin": [ { "gen": { "height": 995540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f010082834e2bb1c0d9e24bffa552ff705ed813aa8e0a31edaae4f9ffe9ebb" } } ], "extra": [ 1, 251, 5, 100, 188, 136, 24, 99, 243, 12, 254, 21, 202, 29, 38, 32, 77, 150, 202, 202, 243, 252, 150, 224, 13, 221, 149, 177, 213, 35, 241, 195, 234, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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