Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5712d3453e230f20491b2d7419fd2273e1120306e0adf0f27dcd72c4acf58d1

Tx prefix hash: b2367826d99043c162abe3ffd3ca23ec3634554d8ac7070d6687a483cea3eda9
Tx public key: d0e5a508e2e0de0023e3fe443041ae8a56dfb42350fd4009fa98a62b8e4d1d7a
Timestamp: 1578647218 Timestamp [UCT]: 2020-01-10 09:06:58 Age [y:d:h:m:s]: 05:296:05:43:08
Block: 42423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359572 RingCT/type: yes/0
Extra: 01d0e5a508e2e0de0023e3fe443041ae8a56dfb42350fd4009fa98a62b8e4d1d7a0211000000118a2ee0d9000000000000000000

1 output(s) for total of 444.054049034000 dcy

stealth address amount amount idx
00: 02671f29cbae213caed84c77aa11b95dda93898a5f887d8967dd4af6c424cfc0 444.054049034000 76428 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": 42433, "vin": [ { "gen": { "height": 42423 } } ], "vout": [ { "amount": 444054049034, "target": { "key": "02671f29cbae213caed84c77aa11b95dda93898a5f887d8967dd4af6c424cfc0" } } ], "extra": [ 1, 208, 229, 165, 8, 226, 224, 222, 0, 35, 227, 254, 68, 48, 65, 174, 138, 86, 223, 180, 35, 80, 253, 64, 9, 250, 152, 166, 43, 142, 77, 29, 122, 2, 17, 0, 0, 0, 17, 138, 46, 224, 217, 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