Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a51279de4626c3fd1b0cd3f74b1c7d560fc98e301a2e371c271959dca11b2a3

Tx prefix hash: 79a88c7582d6c99a112bd5cd47d0d81a4c360be1d8d48380ba381c5c6c8074ab
Tx public key: 50ec3028d43409f0786cc76d612d2328b9e80e079b09350237aa0f2811851fd2
Timestamp: 1707430630 Timestamp [UCT]: 2024-02-08 22:17:10 Age [y:d:h:m:s]: 01:271:02:22:25
Block: 953334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452516 RingCT/type: yes/0
Extra: 0150ec3028d43409f0786cc76d612d2328b9e80e079b09350237aa0f2811851fd202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9058e31ba4450243c8f0ea7b2ba2d726721883c2dca588cbce6c05dae87e255 0.600000000000 1412528 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": 953344, "vin": [ { "gen": { "height": 953334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9058e31ba4450243c8f0ea7b2ba2d726721883c2dca588cbce6c05dae87e255" } } ], "extra": [ 1, 80, 236, 48, 40, 212, 52, 9, 240, 120, 108, 199, 109, 97, 45, 35, 40, 185, 232, 14, 7, 155, 9, 53, 2, 55, 170, 15, 40, 17, 133, 31, 210, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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