Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b11b0f500bba5c9770e638bc40b024499a48b703a6c5b30923ac0216e6aa8174

Tx prefix hash: b8bb871a2c4fbcb5a85a17591d10873172bc534248453aadce9d95bac6faeae3
Tx public key: 916f2c87d6f14fce3ad50a80fb4360ddb94733f9e844343f1f5fd700cb144fa8
Timestamp: 1712843087 Timestamp [UCT]: 2024-04-11 13:44:47 Age [y:d:h:m:s]: 00:339:21:32:12
Block: 998194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243044 RingCT/type: yes/0
Extra: 01916f2c87d6f14fce3ad50a80fb4360ddb94733f9e844343f1f5fd700cb144fa802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8889952cdbb921fb70f7af536430331e57d75e447635fe672a9283a02575cee4 0.600000000000 1458638 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": 998204, "vin": [ { "gen": { "height": 998194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8889952cdbb921fb70f7af536430331e57d75e447635fe672a9283a02575cee4" } } ], "extra": [ 1, 145, 111, 44, 135, 214, 241, 79, 206, 58, 213, 10, 128, 251, 67, 96, 221, 185, 71, 51, 249, 232, 68, 52, 63, 31, 95, 215, 0, 203, 20, 79, 168, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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