Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af6cb3107186ea6a65c65c8357af767ae7889ae800a6d4211da69e182a49664d

Tx prefix hash: 04bb88492665b27ab555bfc5b413f8ae578ad6324fd60035bef3b7f06a702345
Tx public key: d90a743490cb3c8b0338ef0005f7c30c9c5f4bcf54bbc18cba1dca5daa033b31
Timestamp: 1722030720 Timestamp [UCT]: 2024-07-26 21:52:00 Age [y:d:h:m:s]: 00:294:19:45:39
Block: 1074383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210654 RingCT/type: yes/0
Extra: 01d90a743490cb3c8b0338ef0005f7c30c9c5f4bcf54bbc18cba1dca5daa033b3102110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67c4b3145bf4ff3d13d8af07996f171bf76a077097c58a10f8ff9435788300f1 0.600000000000 1546896 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": 1074393, "vin": [ { "gen": { "height": 1074383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67c4b3145bf4ff3d13d8af07996f171bf76a077097c58a10f8ff9435788300f1" } } ], "extra": [ 1, 217, 10, 116, 52, 144, 203, 60, 139, 3, 56, 239, 0, 5, 247, 195, 12, 156, 95, 75, 207, 84, 187, 193, 140, 186, 29, 202, 93, 170, 3, 59, 49, 2, 17, 0, 0, 0, 13, 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