Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0475e454ae24811a8d41e1063a937cf6f692877103768fe9719e8b505f86b88

Tx prefix hash: 401c734a21104c35fa7771a091144d8ab5ed52ef8d762a314d845b99afcc0246
Tx public key: 165401dd8dc19e2c817b9146d4f6081c731a80468774917a3e835a48a6b81c0b
Timestamp: 1708217696 Timestamp [UCT]: 2024-02-18 00:54:56 Age [y:d:h:m:s]: 01:050:12:24:05
Block: 959868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297132 RingCT/type: yes/0
Extra: 01165401dd8dc19e2c817b9146d4f6081c731a80468774917a3e835a48a6b81c0b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f9de9d895d5f2d710a88cc41030122332feae56681f551814c9ba9b8473a630 0.600000000000 1419427 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": 959878, "vin": [ { "gen": { "height": 959868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f9de9d895d5f2d710a88cc41030122332feae56681f551814c9ba9b8473a630" } } ], "extra": [ 1, 22, 84, 1, 221, 141, 193, 158, 44, 129, 123, 145, 70, 212, 246, 8, 28, 115, 26, 128, 70, 135, 116, 145, 122, 62, 131, 90, 72, 166, 184, 28, 11, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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