Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c989e627084d97d2024f21c0a29b332376cc71ed4b28bbf4a6722c3fd826ee

Tx prefix hash: c34172dd3b83f3031f41b8ef5ddd067efc3f271c6303ddcb72419e8f263dc24a
Tx public key: 40ef2b2766ea254460a3dac626ddaf7de4e0d1618fb543fb8557f1f991d74e30
Timestamp: 1722847381 Timestamp [UCT]: 2024-08-05 08:43:01 Age [y:d:h:m:s]: 00:080:02:30:57
Block: 1081153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57354 RingCT/type: yes/0
Extra: 0140ef2b2766ea254460a3dac626ddaf7de4e0d1618fb543fb8557f1f991d74e30021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8cd230c49c04b0270a2c15be958e937119ec9c91880da2c3e8bc9932c21a7e4 0.600000000000 1554792 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": 1081163, "vin": [ { "gen": { "height": 1081153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8cd230c49c04b0270a2c15be958e937119ec9c91880da2c3e8bc9932c21a7e4" } } ], "extra": [ 1, 64, 239, 43, 39, 102, 234, 37, 68, 96, 163, 218, 198, 38, 221, 175, 125, 228, 224, 209, 97, 143, 181, 67, 251, 133, 87, 241, 249, 145, 215, 78, 48, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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