Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b56ecc065aa17341488c6a55d177322df23e751129824f71da3de17268a04e

Tx prefix hash: b4d1d6bdc03f6a32dfdffb9bd1c82b5286fde72ece5482f39c869c4479fc4c20
Tx public key: 0bffc1a8b3df183ed8b02d3f42b6a898681cadc965c7dcc2b7f2a9c6f16a69a5
Timestamp: 1717513842 Timestamp [UCT]: 2024-06-04 15:10:42 Age [y:d:h:m:s]: 00:299:17:53:51
Block: 1036957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214203 RingCT/type: yes/0
Extra: 010bffc1a8b3df183ed8b02d3f42b6a898681cadc965c7dcc2b7f2a9c6f16a69a502110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cffa7137c20103d7f4c47a368ad7fa47465fc46fa3db0e3b3757e0a9992fe109 0.600000000000 1505488 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": 1036967, "vin": [ { "gen": { "height": 1036957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cffa7137c20103d7f4c47a368ad7fa47465fc46fa3db0e3b3757e0a9992fe109" } } ], "extra": [ 1, 11, 255, 193, 168, 179, 223, 24, 62, 216, 176, 45, 63, 66, 182, 168, 152, 104, 28, 173, 201, 101, 199, 220, 194, 183, 242, 169, 198, 241, 106, 105, 165, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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