Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cce69483d15acb4bde093af0bd2f910709162691369383baf5a8cdfa8de5826a

Tx prefix hash: 3dab7f27c1a74b48d69e8b355a8752c2cff997381b7cce40dc1038d76bd5a686
Tx public key: 80b062fa9c7fbbce2f06c297eb7af21c1c47f49e055378b03a8994a1007985f4
Timestamp: 1711516154 Timestamp [UCT]: 2024-03-27 05:09:14 Age [y:d:h:m:s]: 01:022:09:38:16
Block: 987248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276967 RingCT/type: yes/0
Extra: 0180b062fa9c7fbbce2f06c297eb7af21c1c47f49e055378b03a8994a1007985f40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bbb482f79d6c993ee9ef634f5a603cb22b63de3f784d049ef7b25a923e303ca 0.600000000000 1447489 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": 987258, "vin": [ { "gen": { "height": 987248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bbb482f79d6c993ee9ef634f5a603cb22b63de3f784d049ef7b25a923e303ca" } } ], "extra": [ 1, 128, 176, 98, 250, 156, 127, 187, 206, 47, 6, 194, 151, 235, 122, 242, 28, 28, 71, 244, 158, 5, 83, 120, 176, 58, 137, 148, 161, 0, 121, 133, 244, 2, 17, 0, 0, 0, 5, 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