Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94907c9e6e5a4d66baef85588a62e96fc971ee94135233fa0dd5c9e0ea1cd27f

Tx prefix hash: a230699f4d49ec933dcd4f0345024370f1c987fc2027ddf55142e6abf5c9dbea
Tx public key: fd4d7791d06328af109ece7e2ca75cb4cb98b5e440d758b2e80ce9ca0e0147c9
Timestamp: 1699265564 Timestamp [UCT]: 2023-11-06 10:12:44 Age [y:d:h:m:s]: 01:110:08:49:57
Block: 885657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340038 RingCT/type: yes/0
Extra: 01fd4d7791d06328af109ece7e2ca75cb4cb98b5e440d758b2e80ce9ca0e0147c9021100000004faf35c9c000000000000000000

1 output(s) for total of 0.713593211000 dcy

stealth address amount amount idx
00: 6f46517fcbac0f2f0e734d7b8d2d154f6682cdc3860f2bce7736888d08e2492d 0.713593211000 1341438 of 0

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": 885667, "vin": [ { "gen": { "height": 885657 } } ], "vout": [ { "amount": 713593211, "target": { "key": "6f46517fcbac0f2f0e734d7b8d2d154f6682cdc3860f2bce7736888d08e2492d" } } ], "extra": [ 1, 253, 77, 119, 145, 208, 99, 40, 175, 16, 158, 206, 126, 44, 167, 92, 180, 203, 152, 181, 228, 64, 215, 88, 178, 232, 12, 233, 202, 14, 1, 71, 201, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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