Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbcffa60106263cb254d90b0d34caa377ecbe245ef4eac0f3dcbc5cb7045765a

Tx prefix hash: bf94d8287cbc2e94052747fce5d07debc3dc2f0d2e2b65ebf22e86fb7827ff68
Tx public key: cb46db16c874394828f7babdf984f7d489cb674b4f6140c2392d087e9f1c62b1
Timestamp: 1704704323 Timestamp [UCT]: 2024-01-08 08:58:43 Age [y:d:h:m:s]: 01:352:14:29:40
Block: 930735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510890 RingCT/type: yes/0
Extra: 01cb46db16c874394828f7babdf984f7d489cb674b4f6140c2392d087e9f1c62b10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68acd3a0bbb205d7b9e568f9988c834057a4c038c3855dad243f33a29208f746 0.600000000000 1388623 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": 930745, "vin": [ { "gen": { "height": 930735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68acd3a0bbb205d7b9e568f9988c834057a4c038c3855dad243f33a29208f746" } } ], "extra": [ 1, 203, 70, 219, 22, 200, 116, 57, 72, 40, 247, 186, 189, 249, 132, 247, 212, 137, 203, 103, 75, 79, 97, 64, 194, 57, 45, 8, 126, 159, 28, 98, 177, 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