Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af5c0c8543f0262baf2c646db4d63ff51af6648793752e3c97e4eaada7b094fb

Tx prefix hash: d935dc4ca0f19426c16041a0501c18fdc6c6b765620358d5432eeaabee392509
Tx public key: d4436ca2cdf1dcd94206e77e08879a0fd4c785cf68e83339d064e6b37749cf5a
Timestamp: 1695853511 Timestamp [UCT]: 2023-09-27 22:25:11 Age [y:d:h:m:s]: 02:035:00:46:17
Block: 857570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544679 RingCT/type: yes/0
Extra: 01d4436ca2cdf1dcd94206e77e08879a0fd4c785cf68e83339d064e6b37749cf5a021100000005faf35c9c000000000000000000

1 output(s) for total of 0.884126975000 dcy

stealth address amount amount idx
00: f52ee519189f77c98faad70678d2e0e8bcb22ca21c737e7053ee3952c3287ad2 0.884126975000 1311706 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": 857580, "vin": [ { "gen": { "height": 857570 } } ], "vout": [ { "amount": 884126975, "target": { "key": "f52ee519189f77c98faad70678d2e0e8bcb22ca21c737e7053ee3952c3287ad2" } } ], "extra": [ 1, 212, 67, 108, 162, 205, 241, 220, 217, 66, 6, 231, 126, 8, 135, 154, 15, 212, 199, 133, 207, 104, 232, 51, 57, 208, 100, 230, 179, 119, 73, 207, 90, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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