Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88463c782b2a1df687032f5579ccd5dae044d9f10af1d316ed3c4e1923fc2942

Tx prefix hash: 351a84ced1cf9275492b0a57cb346f9e3df1d9e6f1424ca7b4b9c0268febd676
Tx public key: 9ec4063273410b9597989fda1a7ae218fde1988f7efd04e579ae283c43929bdc
Timestamp: 1716548863 Timestamp [UCT]: 2024-05-24 11:07:43 Age [y:d:h:m:s]: 00:243:08:38:02
Block: 1028954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174108 RingCT/type: yes/0
Extra: 019ec4063273410b9597989fda1a7ae218fde1988f7efd04e579ae283c43929bdc02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76163473d7c5ab8b55739f0dc9fbc1bd4d4c51549e62e08561c5308e16ae5486 0.600000000000 1496955 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": 1028964, "vin": [ { "gen": { "height": 1028954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76163473d7c5ab8b55739f0dc9fbc1bd4d4c51549e62e08561c5308e16ae5486" } } ], "extra": [ 1, 158, 196, 6, 50, 115, 65, 11, 149, 151, 152, 159, 218, 26, 122, 226, 24, 253, 225, 152, 143, 126, 253, 4, 229, 121, 174, 40, 60, 67, 146, 155, 220, 2, 17, 0, 0, 0, 3, 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