Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 522b5fa0b29e5f606a9726508876b617f64e6081e34f9e783b6fdc86cc383650

Tx prefix hash: d9cefbdd4d41b9406229c5a6e08d912fa1e2870a9a11f329e5ba8c584a658a55
Tx public key: b3e8735c77314e780f1f3bf24eebbe4e1d2b3552a69c1c171fbcfc39ae9d7f26
Timestamp: 1706103507 Timestamp [UCT]: 2024-01-24 13:38:27 Age [y:d:h:m:s]: 01:070:22:14:10
Block: 942319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311786 RingCT/type: yes/0
Extra: 01b3e8735c77314e780f1f3bf24eebbe4e1d2b3552a69c1c171fbcfc39ae9d7f2602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66c2d6e366fc4ff119ff1d295578074ac1bfab9a55d623d8091a7c21f2e6fe4b 0.600000000000 1400489 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": 942329, "vin": [ { "gen": { "height": 942319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66c2d6e366fc4ff119ff1d295578074ac1bfab9a55d623d8091a7c21f2e6fe4b" } } ], "extra": [ 1, 179, 232, 115, 92, 119, 49, 78, 120, 15, 31, 59, 242, 78, 235, 190, 78, 29, 43, 53, 82, 166, 156, 28, 23, 31, 188, 252, 57, 174, 157, 127, 38, 2, 17, 0, 0, 0, 2, 82, 212, 126, 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