Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58ad5fd6d4b0fe3d4c2d7d5e043e66df82cdca9d57897bca7d4d6ce024ce0923

Tx prefix hash: 5caa4ab126d57ad96415c448d0571cc8b1c8d280e8c11bf0eaa0ed039f344884
Tx public key: 01319c5df7a6875b1229bde686795207533acd1e9b80bfbe4630c11fd7e5b5f0
Timestamp: 1717782272 Timestamp [UCT]: 2024-06-07 17:44:32 Age [y:d:h:m:s]: 01:153:12:30:57
Block: 1039176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368281 RingCT/type: yes/0
Extra: 0101319c5df7a6875b1229bde686795207533acd1e9b80bfbe4630c11fd7e5b5f002110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23e623b5c631aeb60d185cddd6f880d725924e2c5e461d179f137cbb45c4bb3e 0.600000000000 1507797 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": 1039186, "vin": [ { "gen": { "height": 1039176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23e623b5c631aeb60d185cddd6f880d725924e2c5e461d179f137cbb45c4bb3e" } } ], "extra": [ 1, 1, 49, 156, 93, 247, 166, 135, 91, 18, 41, 189, 230, 134, 121, 82, 7, 83, 58, 205, 30, 155, 128, 191, 190, 70, 48, 193, 31, 215, 229, 181, 240, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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