Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf53f071ce2d71154328115f17e6b260b7f1556f7751199d399f2dc25402edae

Tx prefix hash: 75f8491219f53c6de9fc2bff3e33da616e2dcdcb7d49604365d9af7932fc4c31
Tx public key: dd3cf03c03fb5d96a029c82335dd0d7ba98d01eb61124c62129fc43242052de2
Timestamp: 1675220477 Timestamp [UCT]: 2023-02-01 03:01:17 Age [y:d:h:m:s]: 02:077:12:31:14
Block: 687175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 577062 RingCT/type: yes/0
Extra: 01dd3cf03c03fb5d96a029c82335dd0d7ba98d01eb61124c62129fc43242052de20211000000025029cbac000000000000000000

1 output(s) for total of 3.244172191000 dcy

stealth address amount amount idx
00: a92304c94f9b2c7ba15a1dcde3070fedba3ef071ecd84c6b0d4dc6d735e0cba5 3.244172191000 1129731 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": 687185, "vin": [ { "gen": { "height": 687175 } } ], "vout": [ { "amount": 3244172191, "target": { "key": "a92304c94f9b2c7ba15a1dcde3070fedba3ef071ecd84c6b0d4dc6d735e0cba5" } } ], "extra": [ 1, 221, 60, 240, 60, 3, 251, 93, 150, 160, 41, 200, 35, 53, 221, 13, 123, 169, 141, 1, 235, 97, 18, 76, 98, 18, 159, 196, 50, 66, 5, 45, 226, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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