Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 723d6146890749e6f67c93b0f6981a9b7f424f70fedcb8ede25afa29725f0e09

Tx prefix hash: dc19262201b2ca8c5d1aa43c37085309377e67f5433a28c9a4ec0ea8bfce8b52
Tx public key: e8b104e407a8c5dc6630c9f9fd7cad20d57f63aa077031b41651c4f463fb91b8
Timestamp: 1714137310 Timestamp [UCT]: 2024-04-26 13:15:10 Age [y:d:h:m:s]: 00:202:22:36:08
Block: 1008954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145270 RingCT/type: yes/0
Extra: 01e8b104e407a8c5dc6630c9f9fd7cad20d57f63aa077031b41651c4f463fb91b80211000000160011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42573a3e2b2687d7a41fab2c36a4d7e0a6a695cccb9d5c0a3811ccfd8b89354c 0.600000000000 1470476 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": 1008964, "vin": [ { "gen": { "height": 1008954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42573a3e2b2687d7a41fab2c36a4d7e0a6a695cccb9d5c0a3811ccfd8b89354c" } } ], "extra": [ 1, 232, 177, 4, 228, 7, 168, 197, 220, 102, 48, 201, 249, 253, 124, 173, 32, 213, 127, 99, 170, 7, 112, 49, 180, 22, 81, 196, 244, 99, 251, 145, 184, 2, 17, 0, 0, 0, 22, 0, 17, 5, 91, 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