Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9e0627ea8db42da6807c26f85422e142136aa550648a3cc56d7a045771516a1

Tx prefix hash: aac7be9ecc4e27b5e34cd4925cba8d2aa0fb8d9e46c0120bbc9eb671cd8fa1c4
Tx public key: 2821c74588e9101e7d8628e01a190ba0e5ee32558aeb35c83ec96cd11f1631d8
Timestamp: 1582939376 Timestamp [UCT]: 2020-02-29 01:22:56 Age [y:d:h:m:s]: 04:251:08:03:43
Block: 73736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1073260 RingCT/type: yes/0
Extra: 012821c74588e9101e7d8628e01a190ba0e5ee32558aeb35c83ec96cd11f1631d80211000000184ac5aa02000000000000000000

1 output(s) for total of 349.697274995000 dcy

stealth address amount amount idx
00: b894522cbf8d654588cfca9570099a196236c4fecefac388b3798223475aa4a8 349.697274995000 136091 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": 73746, "vin": [ { "gen": { "height": 73736 } } ], "vout": [ { "amount": 349697274995, "target": { "key": "b894522cbf8d654588cfca9570099a196236c4fecefac388b3798223475aa4a8" } } ], "extra": [ 1, 40, 33, 199, 69, 136, 233, 16, 30, 125, 134, 40, 224, 26, 25, 11, 160, 229, 238, 50, 85, 138, 235, 53, 200, 62, 201, 108, 209, 31, 22, 49, 216, 2, 17, 0, 0, 0, 24, 74, 197, 170, 2, 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