Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 402f88d8e02812e6e4e407393497f3e20ae14b320b1fb871d83964b02dedf432

Tx prefix hash: 98b1df8796fdd193aefd7ec173b34413c06bd85ab5d06e8609dbd5ebf64c523c
Tx public key: f2f82153461e50a9dcb5b2bfb7b76594ded6d84ccfdf56ffe945f4e2bc7f3a3f
Timestamp: 1732417580 Timestamp [UCT]: 2024-11-24 03:06:20 Age [y:d:h:m:s]: 00:120:16:59:16
Block: 1160408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86067 RingCT/type: yes/0
Extra: 01f2f82153461e50a9dcb5b2bfb7b76594ded6d84ccfdf56ffe945f4e2bc7f3a3f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cfcf82ca36da7cda7d52ccb1c76af9149680e1655cb6ae1f80d4cbcb74d992e 0.600000000000 1646055 of 15

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": 1160418, "vin": [ { "gen": { "height": 1160408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cfcf82ca36da7cda7d52ccb1c76af9149680e1655cb6ae1f80d4cbcb74d992e" } } ], "extra": [ 1, 242, 248, 33, 83, 70, 30, 80, 169, 220, 181, 178, 191, 183, 183, 101, 148, 222, 214, 216, 76, 207, 223, 86, 255, 233, 69, 244, 226, 188, 127, 58, 63, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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