Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02589b0d2cc959dfbe0eeaf976baca5b439daf31e869af2ebe7a5b8be50c836a

Tx prefix hash: 7f0ac97e81790d0ce8b32c15d19a3f41113e29e7778454362bf9807310443589
Tx public key: d7a6f413cbdd8a25eb741e15309a21e5e8df9fe9cb8552352254abfad2eebe0c
Timestamp: 1702667126 Timestamp [UCT]: 2023-12-15 19:05:26 Age [y:d:h:m:s]: 01:113:00:57:23
Block: 913852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341914 RingCT/type: yes/0
Extra: 01d7a6f413cbdd8a25eb741e15309a21e5e8df9fe9cb8552352254abfad2eebe0c02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db48e43732823871325a0b394e5f64471f2e8ca8f7b0359d40ef86f7938a4be 0.600000000000 1371132 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": 913862, "vin": [ { "gen": { "height": 913852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db48e43732823871325a0b394e5f64471f2e8ca8f7b0359d40ef86f7938a4be" } } ], "extra": [ 1, 215, 166, 244, 19, 203, 221, 138, 37, 235, 116, 30, 21, 48, 154, 33, 229, 232, 223, 159, 233, 203, 133, 82, 53, 34, 84, 171, 250, 210, 238, 190, 12, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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