Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c3e303df600aedef94ab6a75bcbd6021e0d58ed0f4cf4e3407cad8997892291

Tx prefix hash: dfc0df49ffc599e11703862b4cc744bcd810740a8506e727c32ca86a7fe707be
Tx public key: d312d9d0553ce614cc892f898750aa7f1f2b29cd6a34019de99324d64c68cf76
Timestamp: 1728644651 Timestamp [UCT]: 2024-10-11 11:04:11 Age [y:d:h:m:s]: 00:217:03:18:04
Block: 1129229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154997 RingCT/type: yes/0
Extra: 01d312d9d0553ce614cc892f898750aa7f1f2b29cd6a34019de99324d64c68cf7602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fff35968a7c3305ec7026c31468b10b8f9ef5b1cbdded27d25e8d616d1ae64f7 0.600000000000 1612054 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": 1129239, "vin": [ { "gen": { "height": 1129229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fff35968a7c3305ec7026c31468b10b8f9ef5b1cbdded27d25e8d616d1ae64f7" } } ], "extra": [ 1, 211, 18, 217, 208, 85, 60, 230, 20, 204, 137, 47, 137, 135, 80, 170, 127, 31, 43, 41, 205, 106, 52, 1, 157, 233, 147, 36, 214, 76, 104, 207, 118, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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