Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71b02222563dc7062a596397a0bdd5f0bf80c4d9279e83dfe6439dd995ee678a

Tx prefix hash: af422c8807d372a1a10b1558f4cf494c97dafab103ea377701d999d549a3d4b5
Tx public key: dc0fbd7ce5fd4f5718f1e23f1a343ae7ec490f9bf76d250f1ab67d53c88d97f2
Timestamp: 1696570172 Timestamp [UCT]: 2023-10-06 05:29:32 Age [y:d:h:m:s]: 01:098:21:11:02
Block: 863511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331929 RingCT/type: yes/0
Extra: 01dc0fbd7ce5fd4f5718f1e23f1a343ae7ec490f9bf76d250f1ab67d53c88d97f202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.844947321000 dcy

stealth address amount amount idx
00: b3577b8b81fe8afd06c3aa30efe0d7041b7b7240909f60a39472954ab50e37d4 0.844947321000 1317967 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": 863521, "vin": [ { "gen": { "height": 863511 } } ], "vout": [ { "amount": 844947321, "target": { "key": "b3577b8b81fe8afd06c3aa30efe0d7041b7b7240909f60a39472954ab50e37d4" } } ], "extra": [ 1, 220, 15, 189, 124, 229, 253, 79, 87, 24, 241, 226, 63, 26, 52, 58, 231, 236, 73, 15, 155, 247, 109, 37, 15, 26, 182, 125, 83, 200, 141, 151, 242, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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