Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f322f7f7e1689085e5104f9e8bb39e55a0cca8f778293e12694d279eb3da7e4

Tx prefix hash: 69b0f57d78033f1d59a7260f8714ea31c155558e4fb45d0d6725eb5cb16ff86f
Tx public key: dd5f62d21426df73d6b75c16831a58f43b2d3892a61be10655f3f24979d67c1e
Timestamp: 1584923449 Timestamp [UCT]: 2020-03-23 00:30:49 Age [y:d:h:m:s]: 04:248:09:25:59
Block: 86993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074335 RingCT/type: yes/0
Extra: 01dd5f62d21426df73d6b75c16831a58f43b2d3892a61be10655f3f24979d67c1e02110000009848d4d863000000000000000000

1 output(s) for total of 316.050773962000 dcy

stealth address amount amount idx
00: 3321e8c9406c89e8dbdb433a251fb3ebf08e2988f4bd21e28dd2a7db5b26478d 316.050773962000 156867 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": 87003, "vin": [ { "gen": { "height": 86993 } } ], "vout": [ { "amount": 316050773962, "target": { "key": "3321e8c9406c89e8dbdb433a251fb3ebf08e2988f4bd21e28dd2a7db5b26478d" } } ], "extra": [ 1, 221, 95, 98, 210, 20, 38, 223, 115, 214, 183, 92, 22, 131, 26, 88, 244, 59, 45, 56, 146, 166, 27, 225, 6, 85, 243, 242, 73, 121, 214, 124, 30, 2, 17, 0, 0, 0, 152, 72, 212, 216, 99, 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