Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7af471f00799763dbe798f86f3ce1beec766446db5bf8c7bcfd47dbc457d7302

Tx prefix hash: fe1fb267b91bf99e6d7f3b12fb1b4d76ce4411d0c4530dbdf1712388ed02a70b
Tx public key: 55331aa76d917d8825fba57dd96ea575910f77f4829d5b2f74f7a3371e99f36e
Timestamp: 1730706926 Timestamp [UCT]: 2024-11-04 07:55:26 Age [y:d:h:m:s]: 00:020:00:09:42
Block: 1146230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14325 RingCT/type: yes/0
Extra: 0155331aa76d917d8825fba57dd96ea575910f77f4829d5b2f74f7a3371e99f36e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81397b19c4138bc3c3100a78ec61d80f0034ec45f2c7aee243faa56bccc35bdb 0.600000000000 1630829 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": 1146240, "vin": [ { "gen": { "height": 1146230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81397b19c4138bc3c3100a78ec61d80f0034ec45f2c7aee243faa56bccc35bdb" } } ], "extra": [ 1, 85, 51, 26, 167, 109, 145, 125, 136, 37, 251, 165, 125, 217, 110, 165, 117, 145, 15, 119, 244, 130, 157, 91, 47, 116, 247, 163, 55, 30, 153, 243, 110, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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