Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 153b5b5694d016c0b7a05744cc4a028dcb47b06651c5f7e030ca81ef6598eb56

Tx prefix hash: edc6ee1e741bd451f4a23c80465e21d15acf4facfd80ef23cbd8e681ad451420
Tx public key: ff45a177ab20e0da4393ce32040969b0d2d3a0e857cd9e7298829e6a483f838a
Timestamp: 1712807882 Timestamp [UCT]: 2024-04-11 03:58:02 Age [y:d:h:m:s]: 00:360:04:24:01
Block: 997903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257531 RingCT/type: yes/0
Extra: 01ff45a177ab20e0da4393ce32040969b0d2d3a0e857cd9e7298829e6a483f838a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52fc86dce50ea1edcb9aa5dd782950d5bed1575a9d0f9ec56270615c621c79f5 0.600000000000 1458337 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": 997913, "vin": [ { "gen": { "height": 997903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52fc86dce50ea1edcb9aa5dd782950d5bed1575a9d0f9ec56270615c621c79f5" } } ], "extra": [ 1, 255, 69, 161, 119, 171, 32, 224, 218, 67, 147, 206, 50, 4, 9, 105, 176, 210, 211, 160, 232, 87, 205, 158, 114, 152, 130, 158, 106, 72, 63, 131, 138, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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