Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa136d8b0080ea5f1f84a650bb434a8cf4f3989650dd33dfe0cc9a2afc257a09

Tx prefix hash: d93e6c30b349a2721d563ec2e5e29264c7d22ffa5c83f90141def68bd4f72646
Tx public key: cd93c2c42276d96ff4d920cbf11c37c56134e06c84b8d0b58167267513116e16
Timestamp: 1711270622 Timestamp [UCT]: 2024-03-24 08:57:02 Age [y:d:h:m:s]: 01:224:22:34:27
Block: 985208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419430 RingCT/type: yes/0
Extra: 01cd93c2c42276d96ff4d920cbf11c37c56134e06c84b8d0b58167267513116e1602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dddbac25c92b9942137e76dfe493b3d7be9f968b60fbfb0a9650cbd0dfb78674 0.600000000000 1445417 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": 985218, "vin": [ { "gen": { "height": 985208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dddbac25c92b9942137e76dfe493b3d7be9f968b60fbfb0a9650cbd0dfb78674" } } ], "extra": [ 1, 205, 147, 194, 196, 34, 118, 217, 111, 244, 217, 32, 203, 241, 28, 55, 197, 97, 52, 224, 108, 132, 184, 208, 181, 129, 103, 38, 117, 19, 17, 110, 22, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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