Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf025bece21676676a4c24245b1864e87c7eb9ca04a5a64d95bba21f8181694e

Tx prefix hash: ba6cff4a4cd3b65cf1e188daf61589702809c1b4660b1fa89dbd380a33c83d4a
Tx public key: 3848792a66e68f14aa53d370aa7921a5c51e509b0694f3f982f402984a29b873
Timestamp: 1709732215 Timestamp [UCT]: 2024-03-06 13:36:55 Age [y:d:h:m:s]: 01:029:01:40:12
Block: 972439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281772 RingCT/type: yes/0
Extra: 013848792a66e68f14aa53d370aa7921a5c51e509b0694f3f982f402984a29b8730211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9e2ba258416245daecfef2464196f407dfed69bd8db9ad2c63e31af8ff80887 0.600000000000 1432352 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": 972449, "vin": [ { "gen": { "height": 972439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9e2ba258416245daecfef2464196f407dfed69bd8db9ad2c63e31af8ff80887" } } ], "extra": [ 1, 56, 72, 121, 42, 102, 230, 143, 20, 170, 83, 211, 112, 170, 121, 33, 165, 197, 30, 80, 155, 6, 148, 243, 249, 130, 244, 2, 152, 74, 41, 184, 115, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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