Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f94f8b672a5f409f9e559910fcd70eeee4ca04fef00b1b4604fd4b22c79282c

Tx prefix hash: 8e626e0d819eae162d2af6d15eda110933658fe43b0157294540085b2ab5939e
Tx public key: 4555b9e4d88924b5b8bdd9eac2d0cf5a51b2daafa848d1453991d305f5111c08
Timestamp: 1581088060 Timestamp [UCT]: 2020-02-07 15:07:40 Age [y:d:h:m:s]: 04:334:12:47:41
Block: 60468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130733 RingCT/type: yes/0
Extra: 014555b9e4d88924b5b8bdd9eac2d0cf5a51b2daafa848d1453991d305f5111c080211000000030aca7173000000000000000000

1 output(s) for total of 386.941429875000 dcy

stealth address amount amount idx
00: 71e49fa6971efb6b84a5aa67c57955820121317b1cb8da96b2fc4f4ab7203186 386.941429875000 111435 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": 60478, "vin": [ { "gen": { "height": 60468 } } ], "vout": [ { "amount": 386941429875, "target": { "key": "71e49fa6971efb6b84a5aa67c57955820121317b1cb8da96b2fc4f4ab7203186" } } ], "extra": [ 1, 69, 85, 185, 228, 216, 137, 36, 181, 184, 189, 217, 234, 194, 208, 207, 90, 81, 178, 218, 175, 168, 72, 209, 69, 57, 145, 211, 5, 245, 17, 28, 8, 2, 17, 0, 0, 0, 3, 10, 202, 113, 115, 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