Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e19382d59d45dd21c7d080759dd79660f3275e15a76346485ed875da982545a

Tx prefix hash: 658afcdf71e151295b593b219ba102f768a0b516ed50cdf293a4405cdb116b6c
Tx public key: ef174b5f9da7b4fcb0de7674f3382cd01b6d1d27ad67926ac4fb068ce7d284a5
Timestamp: 1724454840 Timestamp [UCT]: 2024-08-23 23:14:00 Age [y:d:h:m:s]: 00:183:15:07:47
Block: 1094498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131051 RingCT/type: yes/0
Extra: 01ef174b5f9da7b4fcb0de7674f3382cd01b6d1d27ad67926ac4fb068ce7d284a5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9804747c44e9c988f011d2cee8a415748f5da98b3c7ff9db068dde097e37b396 0.600000000000 1569615 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": 1094508, "vin": [ { "gen": { "height": 1094498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9804747c44e9c988f011d2cee8a415748f5da98b3c7ff9db068dde097e37b396" } } ], "extra": [ 1, 239, 23, 75, 95, 157, 167, 180, 252, 176, 222, 118, 116, 243, 56, 44, 208, 27, 109, 29, 39, 173, 103, 146, 106, 196, 251, 6, 140, 231, 210, 132, 165, 2, 17, 0, 0, 0, 1, 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