Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03040a7a49a57be4344c91f4cfcd927ed9737fc5a965382511bf81412d8b95bf

Tx prefix hash: 9268cbb7a0eec0c9aeffa8d02e5d0e0e1f834aa3c29e3531c2e479fe7da9afc6
Tx public key: b3f8a83975eb832c09531545aeaedbfd04d36d9da0fc2c2c91ed24960aaea0eb
Timestamp: 1706512857 Timestamp [UCT]: 2024-01-29 07:20:57 Age [y:d:h:m:s]: 01:000:16:34:15
Block: 945717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261553 RingCT/type: yes/0
Extra: 01b3f8a83975eb832c09531545aeaedbfd04d36d9da0fc2c2c91ed24960aaea0eb0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f785284fdf7255c73dd7ceb27fda97f9642cb3745fa6ce852d7267b9a33cf52 0.600000000000 1404035 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": 945727, "vin": [ { "gen": { "height": 945717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f785284fdf7255c73dd7ceb27fda97f9642cb3745fa6ce852d7267b9a33cf52" } } ], "extra": [ 1, 179, 248, 168, 57, 117, 235, 131, 44, 9, 83, 21, 69, 174, 174, 219, 253, 4, 211, 109, 157, 160, 252, 44, 44, 145, 237, 36, 150, 10, 174, 160, 235, 2, 17, 0, 0, 0, 3, 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