Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5d1316172c70703b73da95556fb615596b2bc82c328ddb6730d522eee00832b

Tx prefix hash: 5a07ef073dcb68d8f1d10a67675437bc832d8613f329456deec9a9d419cbb5c0
Tx public key: f8cb04b37edccd249effa4216af99f26d813039f231347455d7665d0191058eb
Timestamp: 1580620069 Timestamp [UCT]: 2020-02-02 05:07:49 Age [y:d:h:m:s]: 05:131:22:21:27
Block: 56877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1246304 RingCT/type: yes/0
Extra: 01f8cb04b37edccd249effa4216af99f26d813039f231347455d7665d0191058eb0211000000012264afe6000000000000000000

1 output(s) for total of 397.689121322000 dcy

stealth address amount amount idx
00: 5fe05aa48620c08802d26d856277f2c2f8e6781cfcf4c0f580a56c7f24b61d6b 397.689121322000 104886 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": 56887, "vin": [ { "gen": { "height": 56877 } } ], "vout": [ { "amount": 397689121322, "target": { "key": "5fe05aa48620c08802d26d856277f2c2f8e6781cfcf4c0f580a56c7f24b61d6b" } } ], "extra": [ 1, 248, 203, 4, 179, 126, 220, 205, 36, 158, 255, 164, 33, 106, 249, 159, 38, 216, 19, 3, 159, 35, 19, 71, 69, 93, 118, 101, 208, 25, 16, 88, 235, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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