Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a41cd2a5d5b0f01542857f41adcba6257c9bef35446d12c20ffc9436054a8018

Tx prefix hash: d38892f09c9f54a85e993c3f3d121eb785cf0b3add31e0aca8f143d07cde0722
Tx public key: 48b35bd305e10023aa927f0f0078be468c2d02f3c8f5840ebc95a7d478f3a5c0
Timestamp: 1724788886 Timestamp [UCT]: 2024-08-27 20:01:26 Age [y:d:h:m:s]: 00:126:18:27:22
Block: 1097249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90679 RingCT/type: yes/0
Extra: 0148b35bd305e10023aa927f0f0078be468c2d02f3c8f5840ebc95a7d478f3a5c0021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65337a083dd98ec3e19ead33642f20dac8b19b53c60280475f25f1bc819c7047 0.600000000000 1572604 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": 1097259, "vin": [ { "gen": { "height": 1097249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65337a083dd98ec3e19ead33642f20dac8b19b53c60280475f25f1bc819c7047" } } ], "extra": [ 1, 72, 179, 91, 211, 5, 225, 0, 35, 170, 146, 127, 15, 0, 120, 190, 70, 140, 45, 2, 243, 200, 245, 132, 14, 188, 149, 167, 212, 120, 243, 165, 192, 2, 17, 0, 0, 0, 3, 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