Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 494dd79441e37f2c99687fbed06ea38009428e679185f482451c317c4299fb93

Tx prefix hash: f5c2d3d9c238a7ff8eaeac58dd513c66b14f3437aff59cf55e66df1ca21ec7e2
Tx public key: 942edf8cc8d8c8a42e4e1c5b7e3ea2299d0694bfd30fc1d0b2c46a6ee6a13a28
Timestamp: 1723767067 Timestamp [UCT]: 2024-08-16 00:11:07 Age [y:d:h:m:s]: 00:238:03:33:02
Block: 1088790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170082 RingCT/type: yes/0
Extra: 01942edf8cc8d8c8a42e4e1c5b7e3ea2299d0694bfd30fc1d0b2c46a6ee6a13a28021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db46ec05b1abb83e8a4c1fe2f1506832bab2703329cb9ad1ff1da738fc74952b 0.600000000000 1563409 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": 1088800, "vin": [ { "gen": { "height": 1088790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db46ec05b1abb83e8a4c1fe2f1506832bab2703329cb9ad1ff1da738fc74952b" } } ], "extra": [ 1, 148, 46, 223, 140, 200, 216, 200, 164, 46, 78, 28, 91, 126, 62, 162, 41, 157, 6, 148, 191, 211, 15, 193, 208, 178, 196, 106, 110, 230, 161, 58, 40, 2, 17, 0, 0, 0, 3, 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