Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c96e78c3c75da8d2f12f1dd01cb085b18b242e5d4e259f3ed089a1feb9dbbafb

Tx prefix hash: e3f6c07140021660ee162ac8f93415c76ab7e22a331658590c49eb648778816e
Tx public key: 311af88b6089e7dfa4bff9fdbea6bd9f27850122bfb22760394f6fe99488838a
Timestamp: 1714415638 Timestamp [UCT]: 2024-04-29 18:33:58 Age [y:d:h:m:s]: 00:344:00:39:05
Block: 1011252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245923 RingCT/type: yes/0
Extra: 01311af88b6089e7dfa4bff9fdbea6bd9f27850122bfb22760394f6fe99488838a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d11089dbb4f0f7fa9d63091a88bb12670d19049c085a272e9a7e52f2fff120a4 0.600000000000 1473434 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": 1011262, "vin": [ { "gen": { "height": 1011252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d11089dbb4f0f7fa9d63091a88bb12670d19049c085a272e9a7e52f2fff120a4" } } ], "extra": [ 1, 49, 26, 248, 139, 96, 137, 231, 223, 164, 191, 249, 253, 190, 166, 189, 159, 39, 133, 1, 34, 191, 178, 39, 96, 57, 79, 111, 233, 148, 136, 131, 138, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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