Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ac5399454a5110d22b187c2cd171ae53dce1d3b10d611e67413bf29b2f75adb

Tx prefix hash: 1983890901e9c2af7c581303fd111be3f7b0a8609dd6d4d2c7a487680725e8bc
Tx public key: 4ccddbd76d3ce7a6122962a6511cf86293dd3f85f452212d3537c039f82e2a77
Timestamp: 1724414545 Timestamp [UCT]: 2024-08-23 12:02:25 Age [y:d:h:m:s]: 00:249:11:05:21
Block: 1094174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178148 RingCT/type: yes/0
Extra: 014ccddbd76d3ce7a6122962a6511cf86293dd3f85f452212d3537c039f82e2a77021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aaff32d3fd4ddcb505eef4c64a3d91a3ad7a07ab430b0fa1ed837bb77bd2f03 0.600000000000 1569263 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": 1094184, "vin": [ { "gen": { "height": 1094174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aaff32d3fd4ddcb505eef4c64a3d91a3ad7a07ab430b0fa1ed837bb77bd2f03" } } ], "extra": [ 1, 76, 205, 219, 215, 109, 60, 231, 166, 18, 41, 98, 166, 81, 28, 248, 98, 147, 221, 63, 133, 244, 82, 33, 45, 53, 55, 192, 57, 248, 46, 42, 119, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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