Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45abd7af32e1dcae0691606b720ae2bccf88a00d6f0386fe8c0f689f991852ae

Tx prefix hash: 598b1ea02a65b68cc0dc98fea2cef0a057cc3b8d1686067b899aa0a722dad0d7
Tx public key: ff0c5f86f6a7e4cff1badaba1e7f7de9ad3cb71a466f42cf0612aecc3bfaf56a
Timestamp: 1677495322 Timestamp [UCT]: 2023-02-27 10:55:22 Age [y:d:h:m:s]: 02:062:01:39:22
Block: 706049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565966 RingCT/type: yes/0
Extra: 01ff0c5f86f6a7e4cff1badaba1e7f7de9ad3cb71a466f42cf0612aecc3bfaf56a021100000001faf35c9c000000000000000000

1 output(s) for total of 2.809095296000 dcy

stealth address amount amount idx
00: 5d1ff811076a91d31755454bd558feb9de64890c91502be74804fe9112d5e354 2.809095296000 1149768 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": 706059, "vin": [ { "gen": { "height": 706049 } } ], "vout": [ { "amount": 2809095296, "target": { "key": "5d1ff811076a91d31755454bd558feb9de64890c91502be74804fe9112d5e354" } } ], "extra": [ 1, 255, 12, 95, 134, 246, 167, 228, 207, 241, 186, 218, 186, 30, 127, 125, 233, 173, 60, 183, 26, 70, 111, 66, 207, 6, 18, 174, 204, 59, 250, 245, 106, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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