Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f844a38a8c8300fc561bbf35f39aa5f5c4072ba73eb43b051420b402fc301e8

Tx prefix hash: bbb7951b04ff0c9313784032aab8a6e3391268d70bdd2c1fee531b91bbc1d12e
Tx public key: b994b2b6cbd7d629cf7ff67cf00ee41cb82d993ecd2db1e15ad68e01c8d59b2f
Timestamp: 1576488521 Timestamp [UCT]: 2019-12-16 09:28:41 Age [y:d:h:m:s]: 05:070:12:35:30
Block: 27904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197163 RingCT/type: yes/0
Extra: 01b994b2b6cbd7d629cf7ff67cf00ee41cb82d993ecd2db1e15ad68e01c8d59b2f02110000000ed81c26c0000000000000000000

1 output(s) for total of 496.070418208000 dcy

stealth address amount amount idx
00: 95eeb9137575f4d70007bbda3d954eee30b871fdab28e79515478accb2207277 496.070418208000 46136 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": 27914, "vin": [ { "gen": { "height": 27904 } } ], "vout": [ { "amount": 496070418208, "target": { "key": "95eeb9137575f4d70007bbda3d954eee30b871fdab28e79515478accb2207277" } } ], "extra": [ 1, 185, 148, 178, 182, 203, 215, 214, 41, 207, 127, 246, 124, 240, 14, 228, 28, 184, 45, 153, 62, 205, 45, 177, 225, 90, 214, 142, 1, 200, 213, 155, 47, 2, 17, 0, 0, 0, 14, 216, 28, 38, 192, 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