Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bd2e8aa2c94dfe64bdf95f0ad064c9471318f69598330fea6f60a7001af0da5

Tx prefix hash: 22a2769396c3b8be0cd174c5ffc5f30e62d8f6fcd4f473767793c06c18c74985
Tx public key: 38de2ae2d222876c6a24f2f6a2b064371994d822b36725112a27787d55191bc9
Timestamp: 1709347027 Timestamp [UCT]: 2024-03-02 02:37:07 Age [y:d:h:m:s]: 01:037:12:33:41
Block: 969241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287823 RingCT/type: yes/0
Extra: 0138de2ae2d222876c6a24f2f6a2b064371994d822b36725112a27787d55191bc90211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd77a38f70520a42ae0c527c738175ba48303a1cf541faf056e57d1504af0362 0.600000000000 1429070 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": 969251, "vin": [ { "gen": { "height": 969241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd77a38f70520a42ae0c527c738175ba48303a1cf541faf056e57d1504af0362" } } ], "extra": [ 1, 56, 222, 42, 226, 210, 34, 135, 108, 106, 36, 242, 246, 162, 176, 100, 55, 25, 148, 216, 34, 179, 103, 37, 17, 42, 39, 120, 125, 85, 25, 27, 201, 2, 17, 0, 0, 0, 6, 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