Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f253b372e737017fb34d526c1f471abb8c435900d9ddd703071dc46b56edf92

Tx prefix hash: 27d696a8395ba555941d294b27e6eecbf1a38bfca3d3c3a111bfa6a8d2935a01
Tx public key: 0b1e76efcd05449d1003c3b20862b0c5fef41a9bad61d390c30b907a4811a479
Timestamp: 1703412408 Timestamp [UCT]: 2023-12-24 10:06:48 Age [y:d:h:m:s]: 01:123:05:33:45
Block: 920041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349206 RingCT/type: yes/0
Extra: 010b1e76efcd05449d1003c3b20862b0c5fef41a9bad61d390c30b907a4811a47902110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6d0c3faaf131abe37e16372b0a7f5b6b4748c83bb9216affd50684a87bbb2d0 0.600000000000 1377719 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": 920051, "vin": [ { "gen": { "height": 920041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6d0c3faaf131abe37e16372b0a7f5b6b4748c83bb9216affd50684a87bbb2d0" } } ], "extra": [ 1, 11, 30, 118, 239, 205, 5, 68, 157, 16, 3, 195, 178, 8, 98, 176, 197, 254, 244, 26, 155, 173, 97, 211, 144, 195, 11, 144, 122, 72, 17, 164, 121, 2, 17, 0, 0, 0, 11, 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