Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76a13f1170997d576396a4414a269e0ea34b526345231793968a83f679fdad44

Tx prefix hash: 735daec2c1e6fb0048cd91138b028d7e0c51427b1447d799d335fbb2c3878850
Tx public key: a621456b057df5bd047b4c8d1bd03d00ca046d1ee3eab5695fdf81eb689b3711
Timestamp: 1720441758 Timestamp [UCT]: 2024-07-08 12:29:18 Age [y:d:h:m:s]: 01:183:19:31:15
Block: 1061224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389972 RingCT/type: yes/0
Extra: 01a621456b057df5bd047b4c8d1bd03d00ca046d1ee3eab5695fdf81eb689b3711021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bd94a1fefc727e2502c634be46edf2f042ad5f5f0a04764966f77934cffc073 0.600000000000 1531715 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": 1061234, "vin": [ { "gen": { "height": 1061224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bd94a1fefc727e2502c634be46edf2f042ad5f5f0a04764966f77934cffc073" } } ], "extra": [ 1, 166, 33, 69, 107, 5, 125, 245, 189, 4, 123, 76, 141, 27, 208, 61, 0, 202, 4, 109, 30, 227, 234, 181, 105, 95, 223, 129, 235, 104, 155, 55, 17, 2, 17, 0, 0, 0, 5, 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