Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e34dcb8c812e656337045b0ac70d09c762828ce946b88835c6b09f0ccc631c

Tx prefix hash: b7633ab0e3d4c82ab9a77ff4d9adb4676ab8dee0a549a5372f0932331ac03346
Tx public key: 6f4e7a88881941f26f78fceff720772927d0d2fbef43302a42933df75b0cd6f2
Timestamp: 1693979143 Timestamp [UCT]: 2023-09-06 05:45:43 Age [y:d:h:m:s]: 01:215:15:21:01
Block: 842006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415233 RingCT/type: yes/0
Extra: 016f4e7a88881941f26f78fceff720772927d0d2fbef43302a42933df75b0cd6f2021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.995599471000 dcy

stealth address amount amount idx
00: 3fdbf3c43b496e4d9b3a4b2bf976a3514b745218c818c1cd36992d768b3d3d49 0.995599471000 1295088 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": 842016, "vin": [ { "gen": { "height": 842006 } } ], "vout": [ { "amount": 995599471, "target": { "key": "3fdbf3c43b496e4d9b3a4b2bf976a3514b745218c818c1cd36992d768b3d3d49" } } ], "extra": [ 1, 111, 78, 122, 136, 136, 25, 65, 242, 111, 120, 252, 239, 247, 32, 119, 41, 39, 208, 210, 251, 239, 67, 48, 42, 66, 147, 61, 247, 91, 12, 214, 242, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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