Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad2edab140fdee6c571c53867de4bea4a6a82babfa93b1f68f984dd94f3cd049

Tx prefix hash: 5637ec71bac96dd8b5ef3b4e0604f81965d5f039f138975e71487f91262d4902
Tx public key: 1ac69392ae325b4f9f36141d33d75ee0c1dbe10f704d090908bcd2aa66b88629
Timestamp: 1705935789 Timestamp [UCT]: 2024-01-22 15:03:09 Age [y:d:h:m:s]: 01:074:20:41:36
Block: 940919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314614 RingCT/type: yes/0
Extra: 011ac69392ae325b4f9f36141d33d75ee0c1dbe10f704d090908bcd2aa66b8862902110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89b96adaa1c60ea9206721f4a3418140fa2aef7a078e6a43d2898277d4c62765 0.600000000000 1399059 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": 940929, "vin": [ { "gen": { "height": 940919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89b96adaa1c60ea9206721f4a3418140fa2aef7a078e6a43d2898277d4c62765" } } ], "extra": [ 1, 26, 198, 147, 146, 174, 50, 91, 79, 159, 54, 20, 29, 51, 215, 94, 224, 193, 219, 225, 15, 112, 77, 9, 9, 8, 188, 210, 170, 102, 184, 134, 41, 2, 17, 0, 0, 0, 8, 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