Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9653b42c3702b6c8f577717128d766d646771d1e6990a7eaf28f54ec44acfef7

Tx prefix hash: 0704169e6bb0697059c0b79eda11f3a57677c930fcec2f1c5189030bd850f73e
Tx public key: 0e431b0eae810ed441dca257e34b6b7325f992428fb4c330601e4e00504e7dbb
Timestamp: 1724273735 Timestamp [UCT]: 2024-08-21 20:55:35 Age [y:d:h:m:s]: 00:302:06:09:23
Block: 1092994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215784 RingCT/type: yes/0
Extra: 010e431b0eae810ed441dca257e34b6b7325f992428fb4c330601e4e00504e7dbb021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cb5a958f32d545f3cfcdae55455b23f392b7f5c362dfe9c313787fef0fe454b 0.600000000000 1567849 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": 1093004, "vin": [ { "gen": { "height": 1092994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cb5a958f32d545f3cfcdae55455b23f392b7f5c362dfe9c313787fef0fe454b" } } ], "extra": [ 1, 14, 67, 27, 14, 174, 129, 14, 212, 65, 220, 162, 87, 227, 75, 107, 115, 37, 249, 146, 66, 143, 180, 195, 48, 96, 30, 78, 0, 80, 78, 125, 187, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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