Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97f56004dac21c76d3dbaba79f4e21e6fa0a2a8a45190d5392e8e46fe702f2c

Tx prefix hash: 0eb3bd5b93009ccba0b2b219858959d919a1e77255699876a04f5fb3e9edab06
Tx public key: b2cbe3267114d96ec618a530d585d0e428498297c3eac74505e961e54bfdec41
Timestamp: 1588737252 Timestamp [UCT]: 2020-05-06 03:54:12 Age [y:d:h:m:s]: 04:303:04:40:46
Block: 99125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132708 RingCT/type: yes/0
Extra: 01b2cbe3267114d96ec618a530d585d0e428498297c3eac74505e961e54bfdec4102110000015145705818000000000000000000

1 output(s) for total of 288.110104147000 dcy

stealth address amount amount idx
00: 702384fcf6a462f35109cd9dc41aa4f1ce039735ba7d9314d282aaaf93b1adf1 288.110104147000 174971 of 0

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": 99135, "vin": [ { "gen": { "height": 99125 } } ], "vout": [ { "amount": 288110104147, "target": { "key": "702384fcf6a462f35109cd9dc41aa4f1ce039735ba7d9314d282aaaf93b1adf1" } } ], "extra": [ 1, 178, 203, 227, 38, 113, 20, 217, 110, 198, 24, 165, 48, 213, 133, 208, 228, 40, 73, 130, 151, 195, 234, 199, 69, 5, 233, 97, 229, 75, 253, 236, 65, 2, 17, 0, 0, 1, 81, 69, 112, 88, 24, 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