Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539d2ba2db160f6d3bbbbff1e6feef6f7f297aa85ca053622162664103172a7f

Tx prefix hash: 1876a24946e46d594866b4f2b8b21f1668240a0546ef9a18ce235da71de8e7d7
Tx public key: e55bfc085f60db7023a1bc67cdd47969df9702e0351be4cf3c46f65dfad89413
Timestamp: 1636868120 Timestamp [UCT]: 2021-11-14 05:35:20 Age [y:d:h:m:s]: 03:119:21:50:46
Block: 373982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864154 RingCT/type: yes/0
Extra: 01e55bfc085f60db7023a1bc67cdd47969df9702e0351be4cf3c46f65dfad8941302110000000906faf294000000000000000000

1 output(s) for total of 35.386920888000 dcy

stealth address amount amount idx
00: 46a0b0a469f9a82de856441d4ca93393b33f0b64fe6a7d2dd6713044249d070b 35.386920888000 757136 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": 373992, "vin": [ { "gen": { "height": 373982 } } ], "vout": [ { "amount": 35386920888, "target": { "key": "46a0b0a469f9a82de856441d4ca93393b33f0b64fe6a7d2dd6713044249d070b" } } ], "extra": [ 1, 229, 91, 252, 8, 95, 96, 219, 112, 35, 161, 188, 103, 205, 212, 121, 105, 223, 151, 2, 224, 53, 27, 228, 207, 60, 70, 246, 93, 250, 216, 148, 19, 2, 17, 0, 0, 0, 9, 6, 250, 242, 148, 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