Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5de2051a1e25ddfaa94654907bbeb39b90b9adc4597edacc69c1348e30b6eadf

Tx prefix hash: 18dd8b3686f2bd399d27520d8ac6cc57d0dcbc5079253d6a0d580678cd4b93f2
Tx public key: 489e593eedc09d927bb34dfb2849b7dbc24ac3d439d8aadc6a826b67d14a1337
Timestamp: 1737425030 Timestamp [UCT]: 2025-01-21 02:03:50 Age [y:d:h:m:s]: 00:298:05:47:50
Block: 1201820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210697 RingCT/type: yes/0
Extra: 01489e593eedc09d927bb34dfb2849b7dbc24ac3d439d8aadc6a826b67d14a1337021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a67ecf6d2f248c61d12dc2ec6efb91bb7abe9a96f2fed22f7613ef27b57cf3 0.600000000000 1688477 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": 1201830, "vin": [ { "gen": { "height": 1201820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a67ecf6d2f248c61d12dc2ec6efb91bb7abe9a96f2fed22f7613ef27b57cf3" } } ], "extra": [ 1, 72, 158, 89, 62, 237, 192, 157, 146, 123, 179, 77, 251, 40, 73, 183, 219, 194, 74, 195, 212, 57, 216, 170, 220, 106, 130, 107, 103, 209, 74, 19, 55, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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