Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96227e6fef290c1ed9eeba741b484985f6fa65b4a3921bed4591dcccc115fa53

Tx prefix hash: 5362bb8fefcc4448ec9b75890c11d274a7f799eb88b34bca4aa49864a27501e5
Tx public key: c4a9b3bd06875d0a3d5145e534206b9f964fbe2f27b6e316c2366fc7bf74d64b
Timestamp: 1648178612 Timestamp [UCT]: 2022-03-25 03:23:32 Age [y:d:h:m:s]: 03:053:23:13:13
Block: 465844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 818744 RingCT/type: yes/0
Extra: 01c4a9b3bd06875d0a3d5145e534206b9f964fbe2f27b6e316c2366fc7bf74d64b0211000000054a0f5013000000000000000000

1 output(s) for total of 17.557622311000 dcy

stealth address amount amount idx
00: b6103626d5e7921c624849d068e5e21eacde4c65ae2d6e45643f777d12d2fd6e 17.557622311000 884033 of 0

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": 465854, "vin": [ { "gen": { "height": 465844 } } ], "vout": [ { "amount": 17557622311, "target": { "key": "b6103626d5e7921c624849d068e5e21eacde4c65ae2d6e45643f777d12d2fd6e" } } ], "extra": [ 1, 196, 169, 179, 189, 6, 135, 93, 10, 61, 81, 69, 229, 52, 32, 107, 159, 150, 79, 190, 47, 39, 182, 227, 22, 194, 54, 111, 199, 191, 116, 214, 75, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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