Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0ae785fab447e2fef9f276e1a1d1acb5a1e63f5e2a1075508bf5bb84d162ca6

Tx prefix hash: 4993226f34e974c6709a27f30fc00bbdafc8d93c935f3f0bb46bd59da27bcc6e
Tx public key: f4816127d15d11e7dd9e63b73e48761db8b2af20b474f00a79548814854fa706
Timestamp: 1720652428 Timestamp [UCT]: 2024-07-10 23:00:28 Age [y:d:h:m:s]: 00:246:16:53:04
Block: 1062969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176261 RingCT/type: yes/0
Extra: 01f4816127d15d11e7dd9e63b73e48761db8b2af20b474f00a79548814854fa706021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c86dddb1cdfe50fab8e5852d47d255e9e5070f81e4f4dd00fdb84d162bc74c9 0.600000000000 1533480 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": 1062979, "vin": [ { "gen": { "height": 1062969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c86dddb1cdfe50fab8e5852d47d255e9e5070f81e4f4dd00fdb84d162bc74c9" } } ], "extra": [ 1, 244, 129, 97, 39, 209, 93, 17, 231, 221, 158, 99, 183, 62, 72, 118, 29, 184, 178, 175, 32, 180, 116, 240, 10, 121, 84, 136, 20, 133, 79, 167, 6, 2, 17, 0, 0, 0, 4, 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