Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c344ba809b90b3c3c392adbe9d82aa71d5557ee1fff849021c5e9bb79e02d62

Tx prefix hash: 2e06f41abb345a4fbc635ff7c2716e63bb63ee6d2f1c2476224154683b865c07
Tx public key: 646e3fe05a743291a59cd907dafc42f9d15f8ccf7e1928d5757ff959e8ae5493
Timestamp: 1746184035 Timestamp [UCT]: 2025-05-02 11:07:15 Age [y:d:h:m:s]: 00:198:08:21:08
Block: 1274114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139469 RingCT/type: yes/0
Extra: 01646e3fe05a743291a59cd907dafc42f9d15f8ccf7e1928d5757ff959e8ae54930211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4b2d8437c14acf10a118ea27d9228cc97c8037a5b1bd54e9c90848f193a1ba9 0.600000000000 1761405 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": 1274124, "vin": [ { "gen": { "height": 1274114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4b2d8437c14acf10a118ea27d9228cc97c8037a5b1bd54e9c90848f193a1ba9" } } ], "extra": [ 1, 100, 110, 63, 224, 90, 116, 50, 145, 165, 156, 217, 7, 218, 252, 66, 249, 209, 95, 140, 207, 126, 25, 40, 213, 117, 127, 249, 89, 232, 174, 84, 147, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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