Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc0e4877ef5bdba9158aa16710dabf4d51831056523e114fa5d0795c63059e7c

Tx prefix hash: 0c7989a432fe5253a56306e30c828af3b487f49a3ea91b6171d090e4b4b35a4f
Tx public key: e1fa01cd4b144d5bf2d4927f1114085589a6a34e5bc0a5ad8575832c2466ccfb
Timestamp: 1732171438 Timestamp [UCT]: 2024-11-21 06:43:58 Age [y:d:h:m:s]: 00:174:06:02:00
Block: 1158361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124396 RingCT/type: yes/0
Extra: 01e1fa01cd4b144d5bf2d4927f1114085589a6a34e5bc0a5ad8575832c2466ccfb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5c61ac0e044619654307d4110df07a536bc86efea0f81fcc97e7e4d64a02ac1 0.600000000000 1643990 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": 1158371, "vin": [ { "gen": { "height": 1158361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5c61ac0e044619654307d4110df07a536bc86efea0f81fcc97e7e4d64a02ac1" } } ], "extra": [ 1, 225, 250, 1, 205, 75, 20, 77, 91, 242, 212, 146, 127, 17, 20, 8, 85, 137, 166, 163, 78, 91, 192, 165, 173, 133, 117, 131, 44, 36, 102, 204, 251, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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