Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c686942e4c961f8fe972f7721b142e1f314c6b35fdc6be41a2c8218d087b86b

Tx prefix hash: 04043bc8e3258360f92e9758c6378febba1b8f5157e4026b60b02ad54c99e8b7
Tx public key: 7a9a74d66400b56e358662a50a9d809f5256d965e5c43432233b61ba10ad2547
Timestamp: 1729806498 Timestamp [UCT]: 2024-10-24 21:48:18 Age [y:d:h:m:s]: 01:027:02:46:57
Block: 1138813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277773 RingCT/type: yes/0
Extra: 017a9a74d66400b56e358662a50a9d809f5256d965e5c43432233b61ba10ad2547021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71c801b44e8e635e4044e1c8612f64e93a6507a4786307989fad329c5ff8b71c 0.600000000000 1622540 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": 1138823, "vin": [ { "gen": { "height": 1138813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71c801b44e8e635e4044e1c8612f64e93a6507a4786307989fad329c5ff8b71c" } } ], "extra": [ 1, 122, 154, 116, 214, 100, 0, 181, 110, 53, 134, 98, 165, 10, 157, 128, 159, 82, 86, 217, 101, 229, 196, 52, 50, 35, 59, 97, 186, 16, 173, 37, 71, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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