Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84241211f8d0ba2a1c2380c9651dd91d693a4d17f391cd8cd056396d56179c51

Tx prefix hash: 1feb8796a5ac59ce3b636e22d2b05243a3166223db404d67f9c1e9e348198077
Tx public key: 9727075d50424f741fde98484be1b9c775705adaa35ea12d275b7e3cbcbc6215
Timestamp: 1580775158 Timestamp [UCT]: 2020-02-04 00:12:38 Age [y:d:h:m:s]: 05:072:21:57:31
Block: 57954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204329 RingCT/type: yes/0
Extra: 019727075d50424f741fde98484be1b9c775705adaa35ea12d275b7e3cbcbc62150211000000068a2ee0d9000000000000000000

1 output(s) for total of 394.434742599000 dcy

stealth address amount amount idx
00: 5acc6d1dd9f6e7e598144d37bedec133e26d8e40d82095ad694eb4512b22e63a 394.434742599000 107189 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": 57964, "vin": [ { "gen": { "height": 57954 } } ], "vout": [ { "amount": 394434742599, "target": { "key": "5acc6d1dd9f6e7e598144d37bedec133e26d8e40d82095ad694eb4512b22e63a" } } ], "extra": [ 1, 151, 39, 7, 93, 80, 66, 79, 116, 31, 222, 152, 72, 75, 225, 185, 199, 117, 112, 90, 218, 163, 94, 161, 45, 39, 91, 126, 60, 188, 188, 98, 21, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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