Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8be1d33aade7efb5e263e6823a66e37ae2b5e635c4efd3519a095855953f3b3f

Tx prefix hash: 0cf407714b365f5b6c29d74e9d1009209da5b01f949a56ecff2afa0fcb626855
Tx public key: a1a52ca550321911e704a5de0bef12713fa2de767b861fe8a701546fd1406006
Timestamp: 1588734148 Timestamp [UCT]: 2020-05-06 03:02:28 Age [y:d:h:m:s]: 04:242:14:24:12
Block: 98701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090032 RingCT/type: yes/0
Extra: 01a1a52ca550321911e704a5de0bef12713fa2de767b861fe8a701546fd14060060211000000036fa03929000000000000000000

1 output(s) for total of 289.043613578000 dcy

stealth address amount amount idx
00: 4e8650ff23e26fec1d6e28f60ca4ca5cbc752b060de5539a91b4a6b06c46c4a7 289.043613578000 174431 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": 98711, "vin": [ { "gen": { "height": 98701 } } ], "vout": [ { "amount": 289043613578, "target": { "key": "4e8650ff23e26fec1d6e28f60ca4ca5cbc752b060de5539a91b4a6b06c46c4a7" } } ], "extra": [ 1, 161, 165, 44, 165, 80, 50, 25, 17, 231, 4, 165, 222, 11, 239, 18, 113, 63, 162, 222, 118, 123, 134, 31, 232, 167, 1, 84, 111, 209, 64, 96, 6, 2, 17, 0, 0, 0, 3, 111, 160, 57, 41, 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