Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acde61e71e8a0e7801b872a4f03f13ce56dac3335536e122fe0728f61a1d3a52

Tx prefix hash: 90ad9a2aaa0a5b398a2bdb419de183827d1571116f1496cee4654a117bc69a3d
Tx public key: e5705ff232aa3b68bf655aa780b3699fc4527ca83f602f7be26f5fb20ae3667b
Timestamp: 1707629121 Timestamp [UCT]: 2024-02-11 05:25:21 Age [y:d:h:m:s]: 01:016:00:39:56
Block: 954982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272475 RingCT/type: yes/0
Extra: 01e5705ff232aa3b68bf655aa780b3699fc4527ca83f602f7be26f5fb20ae3667b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e428276e8e10e913eb67f8a2ce0ca7cd0e430a12f118e98042269bd3fc3b9cc 0.600000000000 1414264 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": 954992, "vin": [ { "gen": { "height": 954982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e428276e8e10e913eb67f8a2ce0ca7cd0e430a12f118e98042269bd3fc3b9cc" } } ], "extra": [ 1, 229, 112, 95, 242, 50, 170, 59, 104, 191, 101, 90, 167, 128, 179, 105, 159, 196, 82, 124, 168, 63, 96, 47, 123, 226, 111, 95, 178, 10, 227, 102, 123, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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