Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea2ad49d770cbefd8cc8e9d4086d482b8223e0117c3b88d4ec80b27e8d73ae40

Tx prefix hash: 0e30bda6a3dd40a92450eae0974b9ae83bef8bdb709709c7432a54ec1502c7dd
Tx public key: 1466a9664682f3dfaa0d270de20e804bd9f33169262ab6f51580ca3366ea3f81
Timestamp: 1703980085 Timestamp [UCT]: 2023-12-30 23:48:05 Age [y:d:h:m:s]: 01:136:00:35:38
Block: 924735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358366 RingCT/type: yes/0
Extra: 011466a9664682f3dfaa0d270de20e804bd9f33169262ab6f51580ca3366ea3f810211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 197f7c237cd404d3be89baababac1415e92d6bdb0f704955cba419efa34018c0 0.600000000000 1382491 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": 924745, "vin": [ { "gen": { "height": 924735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "197f7c237cd404d3be89baababac1415e92d6bdb0f704955cba419efa34018c0" } } ], "extra": [ 1, 20, 102, 169, 102, 70, 130, 243, 223, 170, 13, 39, 13, 226, 14, 128, 75, 217, 243, 49, 105, 38, 42, 182, 245, 21, 128, 202, 51, 102, 234, 63, 129, 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