Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4044291dd67a458714f3ed48bfb01dcfa7c1c085850a9f96d09273d48b8d7d72

Tx prefix hash: 2f03aa9bd78424a7fd62da72d5886494cf9b65bfc9c30a4b8aa6178b60cb0971
Tx public key: 8d6671a4b4f97ce8c901a60d48f407f56364f8750416262435255447958661e0
Timestamp: 1734224986 Timestamp [UCT]: 2024-12-15 01:09:46 Age [y:d:h:m:s]: 00:184:15:32:36
Block: 1175394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131678 RingCT/type: yes/0
Extra: 018d6671a4b4f97ce8c901a60d48f407f56364f8750416262435255447958661e00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01ca4d1bddcc0ec86b68d7d3dc9bdc128811a117d30a35d9faa991b7652fb512 0.600000000000 1661669 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": 1175404, "vin": [ { "gen": { "height": 1175394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01ca4d1bddcc0ec86b68d7d3dc9bdc128811a117d30a35d9faa991b7652fb512" } } ], "extra": [ 1, 141, 102, 113, 164, 180, 249, 124, 232, 201, 1, 166, 13, 72, 244, 7, 245, 99, 100, 248, 117, 4, 22, 38, 36, 53, 37, 84, 71, 149, 134, 97, 224, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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