Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5457124f35e74f632560b0f313170e4b3e09319f1d5162c92185a4293f78dc62

Tx prefix hash: 813e8bb31bb62c46f9c43c609a463d6bb747d5d5f90c085aab4d284a218dacbd
Tx public key: 7229b86513632b50148ae6532acf7347ce3b3a9a7a2e89e42caaeee2493adad1
Timestamp: 1705305703 Timestamp [UCT]: 2024-01-15 08:01:43 Age [y:d:h:m:s]: 01:092:14:57:30
Block: 935709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327306 RingCT/type: yes/0
Extra: 017229b86513632b50148ae6532acf7347ce3b3a9a7a2e89e42caaeee2493adad102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 692f4a90381de587afe445d0d9bccd25839c43874fb2d1b77cdad8c3cbdeb252 0.600000000000 1393725 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": 935719, "vin": [ { "gen": { "height": 935709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "692f4a90381de587afe445d0d9bccd25839c43874fb2d1b77cdad8c3cbdeb252" } } ], "extra": [ 1, 114, 41, 184, 101, 19, 99, 43, 80, 20, 138, 230, 83, 42, 207, 115, 71, 206, 59, 58, 154, 122, 46, 137, 228, 44, 170, 238, 226, 73, 58, 218, 209, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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